up: embedded systems - bacnet - specific messages  
embedded systems - bacnet - message formats - whoisWhat links here?
00 01 02 03 04 05 06 07 08 09 10 11
81 0b 00 0c 01 20 ff ff 00 ff 10 08   
ll ll ll ll nn nn nn nn nn nn aa aa




BACnet Virtual Link Control
offsetlengthdatadescription
0042181Type: BACnet/IP (Annex J) (0x81)
004310bFunction: Original-Broadcast-NPDU (0x0b)
0044200 0cBACnet packet length
Building Automation and Control Network NPDU
offsetlengthdatadescription
0046101Version: 0x01 (ASHRAE 135-1995)
0047120Control: 0x20
0... .... = NSDU contains: BACnet APDU, message type field absent.
.0.. .... = Reserved: Shall be zero and is zero.
..1. .... = Destination Specifier: DNET, DLEN and Hop Count present. If DLEN=0: broadcast, dest. address field absent.
...0 .... = Reserved: Shall be zero and is zero.
.... 0... = Source specifier: SNET, SLEN and SADR absent
.... .0.. = Expecting Reply: Other than a BACnet-Confirmed-Request-PDU, segment of BACnet-ComplexACK-PDU or network layer message expecting a reply present.
.... ..0. = Priority: Not a Life Safety or Critical Equipment message.
.... ...0 = Priority: Normal message
00482ff ffDestination Network Address: 65535
005010Destination MAC Layer Address Length: 0 indicates Broadcast on Destination Network
00511ffhop count: 255
Building Automation and Control Network APDU
offsetlengthdatadescription
00521100001 .... = APDU Type: Unconfirmed-REQ (1)
0053108Unconfirmed Service Choice: who-Is (8)


The basic who-is message above can be followed by two context tags to limit responses to a specific range.
embedded systems - bacnet - message formats - whois
filename:embedded systems - bacnet - message formats - whois
filename:embedded%20systems%20%2D%20bacnet%20%2D%20message%20formats%20%2D%20whois
last edit:June 13 2015 20:41:04 (3249 days ago)
ct = 1714989569.000000 = May 06 2024 05:59:29
ft = 1434242464.000000 = June 13 2015 20:41:04
dt = 280747105.000000